Apparatus and method for managing health data

ABSTRACT

An apparatus and method for managing health data through a user terminal are provided. The method includes inputting a user terminal number for identifying the user terminal, and information of a medical instrument for measuring the health data to a management server interworked with the user terminal, receiving, by a receiver, a security type table mapped onto the user terminal number and comprising a security type code for instructing the health data which the medical instrument has measured to be stored in a first memory without security or in a second memory with security, from the management server, and storing the health data in the first memory or the second memory, which the security type code instructs, through determining the security type code of the security type table when the health data is received from the medical instrument.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation application of prior application Ser.No. 14/017,003, filed on Sep. 3, 2013, which claimed the benefit under35 U.S.C. §119(a) of a Korean patent application filed on Aug. 31, 2012in the Korean Intellectual Property Office and assigned Serial No.10-2012-0096550, the entire disclosure of which is hereby incorporatedby reference.

TECHNICAL FIELD

The present disclosure relates to health data. More particularly, thepresent disclosure relates to an apparatus and a method for managinghealth data.

BACKGROUND

As interest in healthcare continues to increase, necessities formanagement of health data are also gradually increasing. Further, inrecent years, demands for services by which smart phone users can managetheir own health data through a smart phone are increasing together witha rapid increase in the number of smart phone users.

Services by which health data measured through a medical instrument,such as a body weight scale, a blood pressure meter, a blood sugarmeter, a electrocardiograph, or a blood analyzer is transferred to anInformation Technology (IT) device, such as a smart phone by applying aNear Field Communication (NFC) technology, and users manage their ownhealth data are currently used. In addition, demands for the servicesare expected to continuously increase together with an increase in thenumber of smart phones in use.

Meanwhile, according to types of health data, some can be made availableto anyone, whereas others should be made available to a specific group,such as a medical team. However, since the health data is currentlyavailable to be shared with anyone, the private health data is notshared with only the medical team but with other persons, which causesproblems, such as private information exposure on the Internet, orimproper use of the private health data by companies hiring employees.Moreover, when a smart phone storing the health data is lost, problemsin management of private health data can occur.

Therefore, a need exists for a method capable of addressing the problemsin management of the health data.

The above information is presented as background information only toassist with an understanding of the present disclosure. No determinationhas been made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the present disclosure.

SUMMARY

Aspects of the present disclosure are to address at least theabove-mentioned problems and/or disadvantages and to provide at leastthe advantages described below. Accordingly, an aspect of the presentdisclosure is to provide an apparatus and a method for managing healthdata by classifying the health data according to security types.

In accordance with an aspect of the present disclosure, a method ofmanaging health data through a user terminal is provided. The methodincludes inputting a user terminal number for identifying the userterminal, and information of a medical instrument for measuring thehealth data to a management server interworked with the user terminal,receiving, by a receiver, a security type table mapped onto the userterminal number and comprising a security type code for instructing thehealth data which the medical instrument has measured to be stored in afirst memory without security or in a second memory with security, fromthe management server, and storing the health data in the first memoryor the second memory, which the security type code instructs, throughdetermining the security type code of the security type table when thehealth data is received from the medical instrument.

In accordance with another aspect of the present disclosure, a method ofmanaging health data through a management server interworked with a userterminal is provided. The method includes receiving, by a receiver, auser terminal number for identifying the user terminal and informationof a medical instrument for measuring the health data, from the userterminal, determining, by a controller, whether or not a security typecode instructs the health data, which the medical instrument measures tobe stored in a first memory without security or a second memory withsecurity is registered in the management server, and issuing, by amanagement unit, a security type table mapped onto the user terminalnumber based on the security type code to transmit the issued securitytype table to the user terminal, when the security type code isregistered in the management server.

In accordance with another aspect of the present disclosure, a method ofmanaging health data measured by a medical instrument through a hospitalserver is provided. The method includes detecting, by a controller, auser terminal number for identifying a user terminal and a table code ofa security type table, which the user terminal manages, from the userterminal, determining, by the controller, whether or not the detectedtable code coincides with a table code of a security type table mappedonto the user terminal number, and sharing, by a transmitter, healthdata stored in a memory with security among health data which the userterminal manages with the user terminal, when the detected table codecoincides with the table code of the security type table mapped onto theuser terminal number.

In accordance with another aspect of the present disclosure, a userterminal for managing health data is provided. The user terminalincludes a first memory without security, a second memory with security,a transmitter configured to transmit a user terminal number foridentifying the user terminal and information of a medical instrumentfor measuring the health data to a management server interworked withthe user terminal, a receiver configured to receive a security typetable mapped onto the user terminal number and comprising a securitytype code for instructing the health data which the medical instrumenthas measured to be stored in the first memory or the second memory, fromthe management server, and to receive the health data from the medicalinstrument, and a controller configured to determine the security typecode of the security type table, and to instruct the health data to bestored in the first memory or the second memory which the security typecode indicates, when the health data is received.

In accordance with another aspect of the present disclosure, amanagement server for managing health data is provided. The managementserver includes a receiver configured to receive a user terminal numberfor identifying a user terminal and information of a medical instrumentfor measuring the health data, from the user terminal, a controllerconfigured to determine whether or not a security type code instructsthe health data which the medical instrument measures to be stored in afirst memory without security or a second memory with security isregistered in the management server, a management unit configured toissue a security type table mapped onto the user terminal number basedon the security type code, when the security type code is registered inthe management server, and a transmitter configured to transmit thesecurity type table to the user terminal.

In accordance with another aspect of the present disclosure, a hospitalserver for managing health data measured by a medical instrument isprovided. The hospital server includes a controller configured to detecta user terminal number for identifying a user terminal and a table codeof a security type table which the user terminal manages, from the userterminal, and to determine whether or not the detected table codecoincides with a table code of a security type table mapped onto theuser terminal number, and a transmitter configured to share health datastored in a memory with security among health data which the userterminal manages with the user terminal, when the detected table codecoincides with the table code of the security type table mapped onto theuser terminal number.

The present disclosure proposes a method of managing health data byclassifying the health data according to security types, therebyovercoming the problem caused by sharing security required health datawith others.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the present disclosure will be more apparent from thefollowing description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 illustrates a security type table for classifying security typesaccording to medical instruments according to an embodiment of thepresent disclosure;

FIG. 2 illustrates a security type table for classifying security typesaccording to measurable health data in a medical instrument according toan embodiment of the present disclosure;

FIG. 3 is a signal flow diagram illustrating a procedure in which healthdata is stored and managed in a user terminal according to a firstembodiment of the present disclosure;

FIG. 4 is a signal flow diagram illustrating a procedure in which healthdata is stored and managed in a user terminal according to a secondembodiment of the present disclosure;

FIG. 5 is a signal flow diagram illustrating a procedure in which a userterminal and a hospital server share security required health dataaccording to an embodiment of the present disclosure;

FIG. 6 is a flowchart illustrating an operation of a user terminal forstoring and managing health data according to an embodiment of thepresent disclosure;

FIG. 7 is a flowchart illustrating an operation of a management serverfor storing and managing health data according to an embodiment of thepresent disclosure;

FIG. 8 is a flowchart illustrating an operation through which a hospitalserver shares security required health data with a user terminalaccording to an embodiment of the present disclosure;

FIG. 9 is a block diagram illustrating a configuration of a userterminal for storing and managing health data according to an embodimentof the present disclosure;

FIG. 10 is a block diagram illustrating a configuration of a managementserver for storing and managing health data according to an embodimentof the present disclosure; and

FIG. 11 is a block diagram illustrating a configuration of a hospitalserver for sharing security required health data with a user terminalaccording to an embodiment of the present disclosure.

Throughout the drawings, it should be noted that like reference numbersare used to depict the same or similar elements, features, andstructures.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the present disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the embodiments described hereincan be made without departing from the scope and spirit of the presentdisclosure. In addition, descriptions of well-known functions andconstructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of the presentdisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of the presentdisclosure is provided for illustration purpose only and not for thepurpose of limiting the present disclosure as defined by the appendedclaims and their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

By the term “substantially” it is meant that the recited characteristic,parameter, or value need not be achieved exactly, but that deviations orvariations, including for example, tolerances, measurement error,measurement accuracy limitations and other factors known to those ofskill in the art, may occur in amounts that do not preclude the effectthe characteristic was intended to provide.

In an embodiment of the present disclosure which will be describedbelow, a method in which, when a user terminal purchases a medicalinstrument and stores health data measured through the medicalinstrument, the corresponding data is stored and managed in mutuallydifferent memories according to security types of health data will beproposed. For example, a method of storing and managing thecorresponding data in mutually different memories according to whetheror not the health data is general data, which can be available toanyone, or security data, which should be available to a specific group,such as a medical team, will be proposed.

Further, in an embodiment of the present disclosure which will bedescribed below, a security type table will be proposed for storing andmanaging health data in mutually different memories according tosecurity types. The security type table may be issued such that thecorresponding security types may be classified by medical instruments ormeasured health data.

FIG. 1 illustrates a security type table for classifying security typesaccording to medical instruments according to an embodiment of thepresent disclosure.

Referring to FIG. 1, a user terminal 160 purchases a medical instrumentfor measuring a user's health status, for example, a body weight scale,a blood pressure meter, a blood sugar meter, a electrocardiograph, ablood analyzer, or the like, through a management server 130, and themanagement server 130 issues and manages a security type table 100corresponding to the medical instrument. Here, although descriptionswill be given with an assumption that the user terminal 160 is a smartphone, it is apparent that the user terminal 160 may be any other ITdevice. Further, it is assumed that the medical instrument is purchasedthrough a sensor shop of an application executed in the smart phone.Here, the sensor shop is a store where the medical instrument is sold,and is managed through the management server 130.

The security type table 100 is a table for indicating security types ofhealth data, for example, a weight, a blood pressure, a blood sugar, anelectrocardiogram, a blood analysis result, or the like, which aremeasured by the medical instruments, and includes information, such as atable code 102, slot numbers (slot #) 104, vendor Identifiers (IDs) 106,usage codes 108, and security type codes 110.

The table code 102 denotes a code for identification of the securitytype table 100, the slot numbers (slot #) 104 denote slot numbers ofslots constituting a flash memory 150, and the vendor IDs 106 denote IDsfor identifying vendors of the flash memory 150.

Here, usage of the slots constituting the flash memory 150 may bedifferentially set according to vendors, and the usage codes 108 denoteusage of the respective slots. For example, ‘0x01’ denotes that slot #0constituting a flash memory of vendor A and slot #N constituting a flashmemory of vendor N are used for storing movie related data, ‘0x 11’denotes that slot #2 constituting a flash memory of vendor B is used forstoring medicine related data, that is, health data, ‘0x1A’ denotes thatslot #2 constituting a flash memory of vendor C is used for storing gamerelated data, and ‘0x20’ denotes that slot #3 constituting a flashmemory of vendor D is used for storing electronic-book (e-book) relateddata.

The security type codes 110 denote security types of health datameasured through the medical instrument. For example, ‘00’ denotes thata type of measured health data corresponds to a type of general data sothat the measured health data should be stored through an open mode, and‘10’ denotes that a type of measured health data corresponds to a typeof security data so that the measured health data should be storedthrough a closed mode. The open mode is a mode of instructing thecorresponding health data to be stored in an open memory, for example, aUniversal Subscriber Identifier Module (USIM) chip, which can be sharedwith anyone, and the closed mode is a mode of instructing thecorresponding health data to be stored in a memory with security, forexample, an Enhanced Media Identification (EMID) flash memory, which canbe shared with a specific group. For example, in the closed mode, thehealth data is stored in the memory with security so that informationstored in the memory cannot be shared before an inherent ID is input,making it possible to basically prevent external access to the healthdata.

For example, it is assumed that the security type table 100 is createdto correspond to a blood analyzer, and at this time, the security typecode 110 of the health data which the usage code 108 ‘0x11’ denotes isset to code ‘10’ denoting the closed mode. Accordingly, the userterminal 160 receiving the security type table 100 from the managementserver 130 stores a blood analysis result measured through the bloodanalyzer in the memory with security.

Meanwhile, the management server 130 manages a plurality of flashmemories inherently constituted according to vendors, and as an exampleof the flash memory 150, a configuration of a flash memory of vendor Bis illustrated. The flash memory 150 is formed of N slots, for example,slot #0 in which movie related data is stored, slot #1 in which e-bookrelated data is stored, slot #2 in which medicine related data isstored, and the like, and it is apparent that data stored in the slotsmay be differently set according to the vendors.

FIG. 2 illustrates a security type table for classifying security typesaccording to measurable health data in a medical instrument according toan embodiment of the present disclosure.

Referring to FIG. 2, a user terminal 260 purchases a medical instrumentfor measuring a user's health status through a management server 230,and the management server 230 issues and manages a security type table200 corresponding to the medical instrument. In FIG. 2, it is assumedthat one medical instrument may measure a plurality of health dataunlike in FIG. 1, and thus, the security type table 200 is made suchthat security types may be classified according to measurable healthdata in the medical instrument.

Here, although descriptions will be given with an assumption that theuser terminal 260 is a smart phone, it is apparent that the userterminal 260 may be any other IT device. Further, it is assumed that themedical instrument is purchased through a sensor shop of an applicationexecuted in the smart phone.

The security type table 200 is a table for indicating the security typesof the health data which are measured in the medical instrument, andincludes information, such as a table code 202, slot numbers (slot #)204, vendor IDs 206, usage codes 208, and security type codes 210.

The table code 202 denotes a code for identification of the securitytype table 200, the slot numbers (slot #) 204 denote slot numbers ofslots constituting a flash memory 250, and the vendor IDs 206 denote IDsfor identifying vendors of the flash memory 250.

Here, usage of the slots constituting the flash memory 250 may bedifferentially set according to vendors, and the usage codes 208 denoteusage of the respective slots. For example, ‘0x01’ denotes that slot #0constituting a flash memory of vendor A and slot #N constituting a flashmemory of vendor N are used for storing movie related data, ‘0x11’denotes that slot #2 constituting a flash memory of vendor B is used forstoring medicine related data, that is, health data, ‘0x1A’ denotes thatslot #2 constituting a flash memory of vendor C is used for storing gamerelated data, and ‘0x20’ denotes that slot #3 constituting a flashmemory of vendor D is used for storing e-book related data.

The security type codes 210 denote security types of a plurality ofhealth data measured through the medical instrument. For example, ‘00’denotes that a type of measured health data corresponds to a type ofgeneral data so that the measured health data should be stored throughan open mode, and ‘10’ denotes that a type of measured health datacorresponds to a type of security data so that the measured health datashould be stored through a closed mode. Here, assuming that the medicalinstrument corresponding to the security type table 200 measures a bloodpressure, a blood analysis result, and a weight, the security type code210 of the blood pressure and the weight which the medical instrumenthas measured is set to code ‘00’ denoting that the measured bloodpressure and weight should be stored through an open mode, and thesecurity type code 210 of the blood analysis result which the medicalinstrument has measured is set to code ‘10’ denoting that the measuredblood analysis result should be stored through a closed mode.Accordingly, the user terminal 260 receiving the security type table 200from the management server 230 stores the health data measured throughthe medical instrument in an open memory or in a memory with securityaccording to the sorts of the health data. For example, the userterminal stores the blood pressure and the weight in a USIM chipcorresponding to the open memory which can be shared with anyone, andstores the blood analysis result in an EMID flash memory correspondingto the memory with security which can be shared with a specific group,among the health data measured through the medical instrument.

Meanwhile, the management server 230 manages a plurality of flashmemories inherently constituted according to vendors, and as an exampleof the flash memory 250, a configuration of a flash memory of vendor Bis illustrated. The flash memory 250 is formed of N slots, for example,slot #0 in which movie related data is stored, slot #1 in which e-bookrelated data is stored, slot #2 in which medicine related data isstored, and the like, and it is apparent that data stored in the slotsmay be differently set according to the vendors.

FIG. 3 is a signal flow diagram illustrating a procedure in which healthdata is stored and managed in a user terminal according to a firstembodiment of the present disclosure.

Referring to FIG. 3, the signal flow diagram includes a user terminal300, a management server 302, a medical instrument 304, and a hospitalserver 306. In FIG. 3, a hospital server 306 sets a security type codeof a medical instrument 304 interworked therewith, and transmits thesecurity type code to the medical instrument 304 in operation 310. Themedical instrument 304 registers the security type code in a managementserver 302 interworked therewith in operation 312.

Here, although the case in which the hospital server 306 sets thesecurity type code of the medical instrument 304 is described as anexample, the medical instrument 304 may directly set and transmit thesecurity type code to the management server 302. Although notillustrated, the hospital server 306 may manage a Personal Health Record(PHR) server, and the PHR server may be located outside or inside thehospital server 306. Further, the PHR server may also set and transmitthe security type code to the management server 302.

A user terminal 300, such as a smart phone, executes an application topurchase a medical instrument through a sensor shop in operation 314,and inputs a user terminal number and information of the purchasedmedical instrument to the management server 302 in operation 316. Here,the user terminal number corresponds to information for identifying theuser terminal, and may be a phone number, a serial number, a preset userpassword, or the like.

Since the management server 302 recognizes in advance the security typecode for the medical instrument 304 as described in operations 310 and312, the management server 302 issues a security type tablecorresponding to medical instrument information at the same time whenthe medical instrument information is input in operation 318. Thesecurity type table is issued to be mapped onto the user terminalnumber, and since the security type table has been described withreference to FIGS. 1 and 2, a description of the security type tablewill be omitted. The security type table is issued to correspond to themedical instrument. When the medical instrument measures one healthdata, the security type table illustrated in FIG. 1 is issued, and whenthe medical instrument measures a plurality of health data, the securitytype table illustrated in FIG. 2 is issued.

The management server 302 transmits the security type table to the userterminal 300 in operation 320, and transmits the user terminal numberreceived in operation 316 and the table code of the security type tableto the hospital server 306 in operation 321. The hospital server 306stores the user terminal number and the table code in operation 323.

Thereafter, when the medical instrument 304 measures health data inoperation 324, the medical instrument 304 wiredly or wirelesslytransmits the measured health data to the user terminal 300 (inoperation 326, and in operation 327, the user terminal 300 determines asecurity type code denoting a security type of the health data measuredthrough the medical instrument 304, in the security type table receivedin operation 320.

In operation 328, the user terminal 300 stores the received health datain a memory according to the security type code determined in operation327. For example, when the security type code denoting the security typeof the health data measured through the medical instrument 304corresponds to ‘00’, the user terminal 300 determines that the measuredhealth data is general data which should be stored through an open mode,and stores the health data in a USIM chip which can be shared withanyone. On the other hand, when the security type code corresponds to‘10’, the user terminal 300 determines that the health data measuredthrough the medical instrument 304 is security data which should bestored through a closed mode, and stores the health data in an EMIDflash memory which can be shared with a specific group, such as amedical team.

As described above, when storing the health data measured through themedical instrument 304, the user terminal 300 stores the general data inthe USIM chip and the security data in the EMID flash memory accordingto the security type code indicated in the security type table tobasically prevent external access to the health data requiring security.Further, the security type table may be issued in the management server302, and the security type code required for issuance of the securitytype table may be set through the medical instrument 304, the hospitalserver 306, or the PHR server.

FIG. 4 is a signal flow diagram illustrating a procedure in which healthdata is stored and managed in a user terminal according to a secondembodiment of the present disclosure.

Referring to FIG. 4, the signal flow diagram includes a user terminal400, a management server 402, a medical instrument 404, and a hospitalserver 406. In FIG. 4, a user terminal 400, such as a smart phone,executes an application to purchase a medical instrument 404 through asensor shop in operation 410, and inputs a user terminal number andinformation of the purchased medical instrument to a management server402 in operation 412. Here, the user terminal number corresponds toinformation for identifying the user terminal, and may be a phonenumber, a serial number, a preset user password, or the like.

Since the management server 402 does not recognize a security type codefor the medical instrument 404, the management server 402 transmits theuser terminal number and the medical instrument information to ahospital server 406 in order to acquire the security type code inoperation 414. The hospital server 406 sets the security type code ofthe medical instrument 404 corresponding to the received medicalinstrument information, issues a security type table corresponding tothe medical instrument 404 in operation 416, and stores a table code ofthe security type table in operation 417.

Since the security type table has been described with reference to FIGS.1 and 2, a description of the security type table will be omitted. Thesecurity type table is issued to correspond to the medical instrument.When the medical instrument measures one health data, the security typetable illustrated in FIG. 1 is issued, and when the medical instrumentmeasures a plurality of health data, the security type table illustratedin FIG. 2 is issued. Further, although not illustrated, the hospitalserver 406 may manage a PHR server, and the PHR server may be locatedoutside or inside the hospital server 406. Moreover, the PHR server mayalso set the security type code.

The hospital server 406 transmits the security type table to themanagement server 402 in operation 418, and the management server 402transmits the received security type table to the user terminal 400 inoperation 420. The user terminal 400 determines the security type codedenoting the security type of the health data measured through themedical instrument 404, in the security type table in operation 422.

Thereafter, when the medical instrument 404 measures health data inoperation 424, the medical instrument 404 wiredly or wirelesslytransmits the measured health data to the user terminal 400 in operation426, and the user terminal 400 stores the received health data in amemory according to the security type code determined in operation 428.For example, when the security type code denoting the security type ofthe health data measured through the medical instrument 404 correspondsto ‘00’, the user terminal 400 determines that the measured health datais general data which should be stored through an open mode, and storesthe health data in a USIM chip which can be shared with anyone. On theother hand, when the security type code corresponds to ‘10’, the userterminal 400 determines that the health data measured through themedical instrument 404 is security data which should be stored through aclosed mode, and stores the health data in an EMID flash memory whichcan be shared with a specific group, such as a medical team.

As described above, when storing the health data measured through themedical instrument 404, the user terminal 400 stores the general data inthe USIM chip and the security data in the EMID flash memory accordingto the security type code indicated in the security type table tobasically prevent external access to the health data requiring security.Further, the security type table may be issued in the management server402, and the security type code required for issuance of the securitytype table may be set through the hospital server 406, or the PHRserver.

The method in which the user terminal stores the corresponding healthdata in the EMID flash memory such that the health data can be sharedwith the specific group, such as a medical team, when the health datameasured through the medical instrument corresponds to the securityrequired data, has been described with reference to FIGS. 3 and 4.Hereinafter, a method in which the user terminal shares the health datastored in the EMID flash memory with the specific group, such as amedical team, for example, the hospital server, will be described withreference to FIG. 5.

FIG. 5 is a signal flow diagram illustrating a procedure in which a userterminal and a hospital server share security required health dataaccording to an embodiment of the present disclosure.

Referring to FIG. 5, the signal flow diagram includes a user terminal500, a management server 502, a medical instrument 504, and a hospitalserver 506. In FIG. 5, a patient visits a hospital to tag the userterminal 500 at the hospital server 506 in operation 510, and thehospital server 506 detects a user terminal number and a table code of asecurity type table which the user terminal 500 manages in operation512.

Although not illustrated, at this time, a hospital server 506 determineswhether or not the determined table code coincides with a table codestored in advance, and when the determined table code coincides with thetable code stored in advance, a security data stored in an EMID flashmemory of the user terminal can be shared. The hospital server 506 hasalready recognized the table code of the security type table mapped ontothe user terminal, and the table code stored in advance implies thetable code of the security type table mapped onto the user terminal.Here, it is assumed that the detected table code coincides with thetable code stored in advance.

In operation 514, the hospital server 506 transmits a security datarequest message for requesting sharing of the security data stored inthe EMID flash memory of the user terminal 500 to the user terminal 500when the table code detected in operation 512 coincides with the tablecode stored in advance. The user terminal 500 transmits the securitydata stored in the EMID flash memory to the hospital server 506 througha security data acknowledgement message for the security data requestmessage in operation 516. For example, the user terminal 500 and thehospital server 506 share the security data stored in the EMID flashmemory through operations 514 and 516. The hospital server 506 updatesthe health data of the user terminal 500 according to the shared healthdata in operation 520.

However, when the table code detected in operation 512 does not coincidewith the table code stored in advance, the hospital server 506 cannotshare the security data stored in the EMID flash memory of the userterminal 500.

FIG. 6 is a flowchart illustrating an operation of a user terminal forstoring and managing health data according to an embodiment of thepresent disclosure.

Referring to FIG. 6, a user terminal, for example, a smart phoneexecutes an application to purchase a medical instrument through asensor shop in operation 602, and proceeds to operation 604 to input auser terminal number and medical instrument information to a managementserver. Here, the user terminal number corresponds to information foridentifying the user terminal, and may be a phone number, a serialnumber, a preset user password, or the like.

The user terminal receives a security type table from the managementserver in operation 606, and proceeds to operation 608 to determine asecurity type code of the security type table. The security type code isa code denoting that data measured through the medical instrumentpurchased in operation 602 is general data which should be storedthrough an open mode, or security data which should be stored through aclosed mode.

In operation 610, the user terminal receives health data measuredthrough the medical instrument purchased in operation 602. In operation612, the user terminal stores the received health data according tosecurity type code determined in operation 608. For example, when thesecurity type code determined in operation 608 corresponds to ‘00’, theuser terminal stores the measured health data in a USIM chip which canbe shared with anyone, and when the security type code corresponds to‘10’, the user terminal stores the measured health data in an EMID flashmemory which can be shared with a specific group, such as a medicalteam.

FIG. 7 is a flowchart illustrating an operation of a management serverfor storing and managing health data according to an embodiment of thepresent disclosure.

Referring to FIG. 7, a management server receives a user terminal numberand information of a medical instrument purchased through a userterminal, from the user terminal in operation 702. The management serverdetermines whether or not a security type code for health data measuredthrough the medical instrument has been registered in operation 704, andwhen the security type code has been registered, proceeds to operation706 to issue a security type table, mapped onto the user terminalnumber, based on the registered security type code. Thereafter, themanagement server transmits the security type table to the user terminalin operation 708. In the determined result of operation 704, the case inwhich the security type code has been registered corresponds to a casein which the management server has recognized in advance the securitytype code for the medical instrument as described with reference to FIG.3.

Meanwhile, when it is determined in operation 704 that the security typecode has not been registered, the management server proceeds tooperation 710 to transmit the user terminal number and the medicalinstrument information to a hospital server. The management serverreceives a security type table issued and transmitted from the hospitalserver in operation 712. In the determined result of operation 704, thecase in which the security type code has not been registered correspondsto a case in which the management server has not recognized the securitytype code for the medical instrument as described with reference to FIG.4.

FIG. 8 is a flowchart illustrating an operation through which a hospitalserver shares security required health data with a user terminalaccording to an embodiment of the present disclosure.

Referring to FIG. 8, a hospital server tags a user terminal in operation802, and proceeds to operation 804 to detect a user terminal number ofthe user terminal, and a table code of a security type table managedthrough the user terminal.

The hospital server determines whether or not the detected table codecoincides with a table code stored in advance, in operation 806. Here,the table code stored in advance implies a table code of the securitytype table mapped onto the user terminal.

When it is determined in operation 806 that the table code detected inoperation 804 coincides with the table code stored in advance, thehospital server proceeds to operation 808 to transmit a security datarequest message for requesting sharing of a security data stored in anEMID flash memory of the user terminal. The hospital server receives thesecurity data stored in the EMID flash memory through a security dataacknowledgement message in operation 810, and proceeds to operation 812to update the health data of the user terminal.

However, when it is determined in operation 806 that the table codedetected in operation 804 does not coincide with the table code storedin advance, the hospital server cannot share the security data stored inthe EMID flash memory with the user terminal.

FIG. 9 is a block diagram illustrating a configuration of a userterminal for storing and managing health data according to an embodimentof the present disclosure.

Referring to FIG. 9, a user terminal 900 includes a receiver 910, acontroller 920, a first memory 930, a second memory 940, and atransmitter 950.

When purchasing a medical instrument, the user terminal 900 transmitsand inputs a user terminal number and medical instrument information toa management server through the transmitter 950, and receives a securitytype table from the management server through the receiver 910. Here,the user terminal number corresponds to information for identifying theuser terminal, and may be a phone number, a serial number, a preset userpassword, or the like.

The controller 920 identifies a security type code of a security typetable when the security type table is transferred from the receiver 910.Thereafter, the controller 920 controls the first and the secondmemories 930 and 940, respectively, according to the previouslydetermined security type code when health data is transferred from thereceiver 910. For example, when the health data is transferred from thereceiver 910, the controller 920 controls such that the health data isstored in a USIM chip which can be shared with anyone, when thepreviously determined security type code corresponds to ‘00’, and thehealth data is stored in an EMID flash memory which can be shared with aspecific group, such as a medical team, when the security type codecorresponds to ‘10’.

FIG. 10 is a block diagram illustrating a configuration of a managementserver for storing and managing health data according to an embodimentof the present disclosure.

Referring to FIG. 10, a management server 1000 includes a receiver 1010,a controller 1020, a management unit 1030, a memory 1040, and atransmitter 1050.

The receiver 1010 of the management server 1000 determines through thecontroller 1020 whether or not a security type code of a security typetable mapped onto a user terminal has been registered in the memory1040, when a user terminal number and information of a medicalinstrument purchased through the user terminal are input from the userterminal. At this time, when it is determined that the security typecode has been registered in the memory 1040, the security type table isissued through the management unit 1030 to be transmitted to the userterminal through the transmitter 1050. Further, the user terminal numberand the table code of the security type table are transmitted to ahospital server through the transmitter 1050.

Meanwhile, when it is determined that the security type code has notbeen registered in the memory 1040, the user terminal number and themedical instrument information are transmitted to the hospital serverthrough the transmitter 1050. Thereafter, a security type tabletransmitted from the hospital server is received through the receiver1010, and the received security type table is transmitted to the userterminal through the transmitter 1050.

FIG. 11 is a block diagram illustrating a configuration of a hospitalserver for sharing security required health data with a user terminalaccording to an embodiment of the present disclosure.

Referring to FIG. 11, a hospital server 1100 includes a controller 1110,a transmitter 1120, a receiver 1130, and a memory 1140.

The receiver 1130 of the hospital server 1100 determines a user terminalnumber and a table code through the controller 1110 when the userterminal number and the table code of a security type table which a userterminal manages are input through tagging of the user terminal.

Moreover, the controller 1110 determines whether or not the determinedtable code coincides with a table code stored in advance, that is, atable code of a security type table mapped onto the user terminal, andwhen the determined table code coincides with the table code stored inadvance, transmits a security data request message for requestingsharing of a security data stored in an EMID flash memory of the userterminal through the transmitter 1120.

Thereafter, a security data acknowledgement message is received in replyto the security data request message through the receiver 1130, and thesecurity data stored in the EMID flash memory of the user terminal isreceived together with the security data acknowledgement message. Thereceived security data is transferred to the memory 1140, and thehospital server 1100 updates health data of the user terminal which isstored in the memory 1140.

The foregoing method for processing a user-customized page of thepresent disclosure may be implemented in an executable program commandform by various computer means and be recorded in a non-transitorycomputer readable recording medium. In this case, the non-transitorycomputer readable recording medium may include a program command, a datafile, and a data structure individually or a combination thereof. In themeantime, the program command recorded in a recording medium may bespecially designed or configured for the present disclosure or be knownto a person having ordinary skill in a computer software field to beused. The non-transitory computer readable recording medium includesMagnetic Media, such as a hard disk, a floppy disk, or a magnetic tape,an Optical Media, such as a Compact Disc Read Only Memory (CD-ROM) or aDigital Versatile Disc (DVD), a Magneto-Optical Media, such as afloptical disk, and a hardware device, such as a ROM, a Random AccessMemory (RAM), a flash memory for storing and executing program commands.The non-transitory computer readable recording medium can also bedistributed over network coupled computer systems so that the computerreadable code is stored and executed in a distributed fashion. Further,the program command includes a machine language code created by acomplier and a high-level language code executable by a computer usingan interpreter. The foregoing hardware device may be configured to beoperated as at least one software module to perform an operation of thepresent disclosure.

Further, it may be appreciated that an apparatus and a method formanaging health data according to embodiments of the present disclosurecan be implemented in software, hardware, or a combination thereof. Forexample, specific electronic components may be employed in a mobiledevice or similar or related circuitry for implementing the functionsassociated with the various embodiments of the present disclosure asdescribed above. Alternatively, one or more processors operating inaccordance with stored instructions may implement the functionsassociated with the various embodiments of the present disclosure asdescribed above. If such is the case, it is within the scope of thepresent disclosure that such instructions may be stored on one or morenon-transitory processor readable mediums. Examples of the processorreadable mediums include a volatile or a non-volatile storage device,such as a ROM, a memory such as a RAM, a memory chip, a memory device,or a memory Integrated Circuit (IC), or a recordable optical or magneticmedium, such as a CD, a DVD, a magnetic disk, or a magnetic tape,regardless of its ability to be erased or its ability to be re-recorded.The processor readable mediums can also be distributed over networkcoupled computer systems so that the instructions are stored andexecuted in a distributed fashion. In addition, functional computerprograms, instructions, and instruction segments for accomplishing thepresent disclosure can be easily construed by programmers skilled in theart to which the present disclosure pertains.

Accordingly, the present disclosure includes a program for a codeimplementing the apparatus and method described in the appended claimsof the specification and a machine (i.e., a computer or thelike)-readable storage medium for storing the program. Moreover, such aprogram as described above can be electronically transferred through anarbitrary medium, such as a communication signal transferred through acable or a wireless connection, and the present disclosure properlyincludes their equivalents.

Moreover, an apparatus for health data management may receive theprogram from a program providing apparatus connected in a wired orwireless method, and store the program. The program providing apparatusmay include a program including instructions allowing a graphicprocessing apparatus to perform a preset content protecting method, amemory for storing information used for the content protecting method, acommunication unit for performing a wired or a wireless communicationwith the graphic processing apparatus, and a controller for transmittinga corresponding program to a transmitter/receiver in response to arequest of the graphic processing apparatus or automatically.

While the present disclosure has been shown and described with referenceto various embodiments thereof, it will be understood by those skilledin the art that various changes in form and details may be made thereinwithout departing from the spirit and scope of the present disclosure asdefined by the appended claims and their equivalents.

What is claimed is:
 1. A method for managing health data by a userterminal, the method comprising: transmitting information of the userterminal for identifying the user terminal, and information of a medicalinstrument for measuring the health data to a management serverinterworked with the user terminal; receiving information comprising asecurity type for instructing the health data measured by the medicalinstrument to be stored in a first memory or a second memory, the secondmemory being accessible by at least one designated user, from themanagement server; and storing the health data in the first memory orthe second memory based on the security type.
 2. The method of claim 1,wherein the security type is included in a security type table, andwherein the security type table comprises at least one of a table codefor identification of the security type table, slot numbers of slotsconstituting the first and the second memories, identifiers foridentifying vendors of the first and the second memories, or usage codesof the slots.
 3. The method of claim 1, wherein the security type is setbased on medical instruments if the medical instrument measures onehealth data, and wherein the security type is set based on health data,which the medical instrument measures, if the medical instrumentmeasures two or more health data.
 4. The method of claim 1, wherein thesecurity type table is received from the management server or a hospitalserver interworked with the management server, wherein the security typeis set in the medical instrument or the hospital server to be registeredin the management server, if the security type table is received fromthe management server, and wherein the security type is set in thehospital server, if the security type table is received from thehospital server.
 5. The method of claim 1, further comprising: receivinga request for sharing of the health data stored in the second memory,from a hospital server interworked with the management server, if atable code of the security type table coincides with a table code of asecurity type table mapped onto the information of the user terminal;and transmitting the health data stored in the second memory to thehospital server.
 6. The method of claim 1, wherein the information ofthe user terminal comprises at least one of a phone number, a serialnumber, or a preset password of the user terminal.
 7. A method formanaging health data by a management server interworked with a userterminal, the method comprising: receiving information of the userterminal for identifying the user terminal and information of a medicalinstrument for measuring the health data, from the user terminal;determining whether or not a security type for instructing the healthdata measured by the medical instrument to be stored in a first memoryor a second memory is registered in the management server, the secondmemory being accessible by at least one designated user; generatinginformation comprising the security type, if the security type isregistered in the management server; and transmitting the information tothe user terminal.
 8. The method of claim 7, further comprising:transmitting the information of the user terminal and the information ofthe medical instrument to a hospital server in which the security typeis stored, if the security type is not registered in the managementserver; and receiving a security type table from the hospital server,and transmitting the received security type table to the user terminal.9. The method of claim 7, wherein the security type is included in asecurity type table, and wherein the security type table comprises atleast one of a table code for identification of the security type table,slot numbers of slots constituting the first and the second memories,identifiers for identifying vendors of the first and the secondmemories, or usage codes of the slots.
 10. The method of claim 7,wherein the security type is set based on medical instruments if themedical instrument measures one health data, and wherein the securitytype is set based on health data which the medical instrument measures,if the medical instrument measures two or more health data.
 11. Themethod of claim 7, wherein the security type is set in the medicalinstrument or a hospital server to be registered in the managementserver.
 12. The method of claim 7, wherein the information of the userterminal comprises at least one of a phone number, a serial number, or apreset password of the user terminal.
 13. A user terminal for managinghealth data, the user terminal comprising: a first memory; a secondmemory being accessible by at least one designated user; a transmitterconfigured to transmit information of the user terminal for identifyingthe user terminal and information of a medical instrument for measuringthe health data to a management server interworked with the userterminal; a receiver configured to: receive information comprising asecurity type for instructing the health data measured by the medicalinstrument to be stored in the first memory or the second memory, fromthe management server, and receive the health data from the medicalinstrument; and at least one processor configured to instruct the healthdata to be stored in the first memory or the second memory based on thesecurity type.
 14. The user terminal of claim 13, wherein the securitytype is included in a security type table, and wherein the security typetable comprises at least one of a table code for identification of thesecurity type table, slot numbers of slots constituting the first andthe second memories, identifiers for identifying vendors of the firstand the second memories, or usage codes denoting usage of the slots. 15.The user terminal of claim 14, wherein the security type table isreceived from the management server or a hospital server interworkedwith the management server, wherein the security type is set in themedical instrument or the hospital server to be registered in themanagement server, if the security type table is received from themanagement server, and wherein the security type is set in the hospitalserver, if the security type table is received from the hospital server.16. The user terminal of claim 14, wherein the receiver receives arequest for sharing of the health data stored in the second memory, froma hospital server interworked with the management server, if a tablecode of the security type table coincides with a table code of asecurity type table mapped onto the information of the user terminal,and wherein the transmitter transmits the health data stored in thesecond memory to the hospital server.
 17. The user terminal of claim 13,wherein the security type is set based on medical instruments if themedical instrument measures one health data, and wherein the securitytype is set based on health data, which the medical instrument measures,if the medical instrument measures two or more health data.
 18. The userterminal of claim 13, wherein the information of the user terminalcomprises at least one of a phone number, a serial number, or a presetpassword of the user terminal.
 19. A management server for managinghealth data, the management server comprising: a receiver configured toreceive information of the a user terminal for identifying a userterminal and information of a medical instrument for measuring thehealth data, from the user terminal; at least one processor configuredto: determine whether or not a security type for instructing the healthdata measured by the medical instrument to be stored in a first memoryor a second memory is registered in the management server, the secondmemory being accessible by at least one designated user, and generateinformation comprising the security type, if the security type isregistered in the management server; and a transmitter configured totransmit the information to the user terminal.
 20. The management serverof claim 19, wherein the transmitter is further configured to: transmitthe information of the user terminal and the information of the medicalinstrument to a hospital server in which the security type is stored, ifthe security type is not registered in the management server, andtransmit a security type table to the user terminal if the receiverreceives the security type table from the hospital server.
 21. Themanagement server of claim 19, wherein the security type is included ina security type table, and wherein the security type table comprises atleast one of a table code for identification of the security type table,slot numbers of slots constituting the first and the second memories,identifiers for identifying vendors of the first and the secondmemories, or usage codes of the slots.
 22. The management server ofclaim 19, wherein the security type is set based on medical instrumentsif the medical instrument measures one health data, and wherein thesecurity type is set based on health data which the medical instrumentmeasures if the medical instrument measures two or more health data. 23.The management server of claim 19, wherein the security type is set inthe medical instrument or a hospital server to be registered in themanagement server.
 24. The management server of claim 19, wherein theinformation of the user terminal comprises at least one of a phonenumber, a serial number, or a preset password of the user terminal. 25.A non-transitory processor readable medium for storing a computerprogram of instructions configured to be readable by at least oneprocessor for instructing the at least one processor to execute acomputer process for performing a method for managing health data in auser terminal, the method comprising: transmitting information of theuser terminal for identifying the user terminal, and information of amedical instrument for measuring the health data to a management serverinterworked with the user terminal; receiving information comprising asecurity type for instructing the health data measured by the medicalinstrument to be stored in a first memory or a second memory, from themanagement server, the second memory being accessible by at least onedesignated user; and storing the health data in the first memory or thesecond memory based on the security type.